CRM For Dummies by Helgeson Lars

Author:Helgeson, Lars [Helgeson, Lars]
Language: eng
Format: epub
ISBN: 9781119368984
Publisher: Wiley
Published: 2017-06-16T04:00:00+00:00

FIGURE 7-13: The four sides of an API.

An API requires the skills of a developer or system integrator with a team of developers. The developer needs to know what your requirements are for integration, and translate those requirements into software that connects all these pieces together.

Choosing master-slave versus master-master

One decision you need to make is how to handle conflicts in data. If one system says one thing but the other system says another, you must have rules in place to make sure your API connections know what to do. You can follow two types of rules:

Master-slave: One system is always correct. If the other gets out of sync, the master always overrides the slave. In this scenario, good data can be overwritten, so make sure you fully understand what it means for your data management. The weakness of this system is that when the master fails, a new system must become the master before any updates to the data can occur.

Master-master: This approach relies on which data set is most up to date. The most recently updated data becomes the master. Setting up master-master control is more difficult. If any system can update any part of your data, you must have strict rules that govern what happens in case of a conflict. You have to account for latency , where a delay in updating could cause issues with overwriting good data.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.